Contribution org.nuxeo.ecm.core.storage.mongodb.configuration--configuration
In component org.nuxeo.ecm.core.storage.mongodb.configuration
org.nuxeo.ecm.core.storage.mongodb.configuration
inside nuxeo-core-storage-mongodb-2023.11.13.jar /OSGI-INF/mongodb-configuration-properties.xml
You can influence this order by adding "require" tags in the containing component declaration, to make sure it is resolved after another component (see "Resolution Order" on components).
This contribution is part of XML component Documentation
Property to disable the fact that on MongoDB a LIKE match anchors its search (like in SQL databases), i.e., absent wildcards, it does not match in the middle of a string.
When true, does not match in the middle of a string. When false, works as if there was a % on each side of the LIKE expression.
@since 10.3
Extension Point
Extension point configuration of component ConfigurationService.Registration Order
22
The registration order represents the order in which this contribution was registered on its target extention
point.
This will impact the override/merge behaviour when it is implemented on the target service, and is useful for
proper customization of existing contributions.
You can influence this order by adding "require" tags in the containing component declaration, to make sure it is resolved after another component (see "Resolution Order" on components).
Contributed Items
XML Source
<extension point="configuration" target="org.nuxeo.runtime.ConfigurationService">
<documentation>
Property to disable the fact that on MongoDB a LIKE match anchors its search
(like in SQL databases), i.e., absent wildcards, it does not match in the middle of a string.
When true, does not match in the middle of a string.
When false, works as if there was a % on each side of the LIKE expression.
@since 10.3
</documentation>
<!-- default is true for 10.3 and later -->
<property name="nuxeo.mongodb.like.anchored">true</property>
</extension>